ABSTRACT System Development has become more and more concentrated on development for the Web and this has resulted in larger target groups. It will most surely continue to be so considering that the Web will be the infrastructure of business and services in the future. A big target group involves that the owner of a system can earn a lot of money from the paying users, but that assumes that the system can meet user needs. If a system on the Web does not satisfy the user?s demands then they will use the competitor?s system instead because it is only a mouse-click away.

ABSTRACT System Development has become more and more concentrated on development for the Web and this has resulted in larger target groups. It will most surely continue to be so considering that the Web will be the infrastructure of business and services in the future. A big target group involves that the owner of a system can earn a lot of money from the paying users, but that assumes that the system can meet user needs. If a system on the Web does not satisfy the user?s demands then they will use the competitor?s system instead because it is only a mouse-click away.

This report describes the development of a system for controlling documents. The report starts with a problem description which the company wants an intranet-based solution for. The report then continues to describe the development phase for the different parts of the system which results in a complete system. The company that wanted this system is called Orbit One and is located in Ronneby, Sweden. They have had a problem with old documents circulating in different versions and in different binders.

AbstractThis paper discusses how System Development methods today support communication between system developers and their customers and end users. Today there are many System Development methodologies with different aims and emphases. It is difficult, however, to find among these methods those who promote good and effective communication with customers because so many of these are very technically rooted and not as much directed towards the soft aspects of systems development - i.e. Human aspects. Our own experiences tells that a simple interview can be initialized without us having an idea what to ask the customer about or how to structure it up - nonetheless it?s done, but the outcome is just chance.

Many research reports mention the fact that a huge number of all System Development projects never reach a successful ending; with other words never fulfil formulated goals. By identifying and forming success factors (and in some aspect risk factors) that the project manager in practice can use, this study may be seen as a step in the direction towards minimising the high number of failed System Development projects. The purpose of this research report is to investigate how a System Development project, where the development process is based on a specific development or process model (in this case the Waterfall model), can and should be driven. I aim to clarify what is demanded of a project leader for the specific development process and give an account for which eventual leadership qualities that can be well suited for given situation in relation to the need for technical competence. Among other things the project manager should inspire confidence, drive, be a decision maker, engage and own some form of basic knowledge in the field of System Development.

Within System Development users have rarely been involved or received much attention during the development. Most of the times, the primary focus within System Development lies on insuring functionality, rather than making the system usable. The literature specifies that a non user-centered approach can contribute to a product with low usability, which can lead to an ineffective and unsatisfactory experience for the end users.The purpose of this thesis is to begin an investigation to see if the use of non user-oriented System Development methods is a possible cause of low usability in the final system.To achieve the purpose of this thesis, we have conducted a case study. Within the case study we examined the usability of a time reporting system. The case study included seven minor studies; an investigation concerning the development of the system, an expert evaluation of the system, interviews and observations of users, developed paper prototypes and executable prototypes, both which user testing was performed on.The result of this study shows that by working with user-entered methods, the usability in the time reporting system increased after the design had been revised.

As part of an internship at Ericsson, this report was written to enhance the understanding of how it is to develop a system that is well established at the workplace. To improve an already existing system is not always as easy as many developers may think. In this report the pros and cons of developing an already existing system has been researched and analyzed. Do note that the results are only from one development of a specific system and that comparison of other developments has been made from other reports and not from experiencing it firsthand. It was found that the choices made can have an impact on further developing and it is important to write down what has been done.

This thesis has been performed for the company System Andersson as a part of the bachelors degree in information technology at the School of Engineering in Jönköping. The thesis is based on the development of an iPhone application.System Andersson has an application for Android that is being used for their MPS system (material and production control system). Their customers, however, have also showed interest in being able to use this application for iPhone.The students handle the subject of iOS developing, including the design of the application, the use of the development language Objective-C, the use of the scripting language of Json used for server connections and SQL.The primary goal with this thesis has been to improve the students knowledge in such subjects as application development for mobile platforms, in such areas as Xcode, which is the development platform that Apple uses and Objective-C, which is the development language being used. The result of this thesis is an almost fully functional iOS application, similar to the Android application with some functionality missing..

The Thesis purpose is in the context of System Development validate the Scrum Methodology. Projects concerning information technology are difficult to manage and tend to fail in quality, time or costs. Scrum presents a new view of the System Development. Better cooperation between customers and developers, continuous follow-up on daily basis and extensive communication in the development team are all characteristics of Scrum. Scrum is described as a new paradigm by its founders but has been criticized by experts of System Development too.

Many research reports mention the fact that a huge number of all system development projects never reach a successful ending; with other words never fulfil formulated goals. By identifying and forming success factors (and in some aspect risk factors) that the project manager in practice can use, this study may be seen as a step in the direction towards minimising the high number of failed System Development projects. The purpose of this research report is to investigate how a System Development project, where the development process is based on a specific development or process model (in this case the Waterfall model), can and should be driven. I aim to clarify what is demanded of a project leader for the specific development process and give an account for which eventual leadership qualities that can be well suited for given situation in relation to the need for technical competence. Among other things the project manager should inspire confidence, drive, be a decision maker, engage and own some form of basic knowledge in the field of System Development.

The development of IT systems is usually accomplished by some form of System Development methodology. It can be performed as the waterfall method, where each phase is completed before the next begins. One of the reasons to follow a development methodology is that the process is more structured, faster and that the product will have higher quality. One risk of not using a System Development approach is that the code can be unstructured and difficult to maintain.This paper describes an alternative method in which the development occurred without the use of any System Development methodology. This has been possible because there was a clear goal of the program that should be developed.

The increasing complexity in the development of a configurable real-time system has emerged new principles of software techniques, such as aspect-oriented software development and component-based software development. These techniques allow encapsulation of the system's crosscutting concerns and increase the modularity of the software. The properties of a component that influences the systems performance or semantics are specified separately in entities called aspects, while basic functionality of the property still remains in the component. When building a real-time system, different sets of configurations of aspects and components can be combined, resulting in different configurations of the system. The temporal behavior of the system changes and a way to ensure the predictability of the system is needed.

This report describes the development of a system for controlling documents. The report starts with a problem description which the company wants an intranet-based solution for. The report then continues to describe the development phase for the different parts of the system which results in a complete system. The company that wanted this system is called Orbit One and is located in Ronneby, Sweden. They have had a problem with old documents circulating in different versions and in different binders. Now thanks to their new system they can access their documents easy and on demand through their intranet..

The purpose of this thesis is to explain one aspect of how and why the development in the third world is lagging behind. The precondition is that development through an agricultural revolution is necessary and that all countries benefit from trading. But these two conditions are not met today. By using the urban-bias and the world system theory I have analysed how the situation appears to be according to the precondition. It appears that both the urban-bias and the world system theory are essential to understand how and why the situation in third world still has not reached the same development phase as most other countries.

The aim of this paper is to examine how The Swedish Library Classification System, also known as the ?SAB-system?, has classified popular music. The investigation is limited to the classification category of ?Yx Jazz, Rock and Popular Music? within the SAB-system. The development of this category is studied.